Methods and devices for treating and/or processing data

ABSTRACT

At the inputs and/or outputs, memories are assigned to a reconfigurable module to achieve decoupling of internal data processing and in particular decoupling of the reconfiguration cycles from the external data streams (to/from peripherals, memories, etc.).

BACKGROUND INFORMATION

The present invention relates to reconfigurable components in general,and in particular but not exclusively the decoupling of data processingwithin the reconfigurable component and/or within parts of thereconfigurable component and data streams, specifically both within thereconfigurable component and also to and from peripherals, massmemories, host processors, and the like (see, e.g., German PatentApplication Nos. DE 101 10 530.4 and DE 102 02 044.2).

Memories are assigned to a reconfigurable module (VPU) at the inputsand/or outputs to achieve decoupling of internal data processing, thereconfiguration cycles in particular, from the external data streams(to/from peripherals, memories, etc.).

Reconfigurable architecture includes modules (VPUs) having aconfigurable function and/or interconnection, in particular integratedmodules having a plurality of unidimensionally or multidimensionallypositioned arithmetic and/or logic and/or analog and/or storage and/orinternally/externally interconnecting modules, which are interconnecteddirectly or via a bus system.

These generic modules include in particular systolic arrays, neuralnetworks, multiprocessor systems, processors having a plurality ofarithmetic units and/or logic cells and/or communication/peripheralcells (IO), interconnecting and networking modules such as crossbarswitches, as well as conventional modules including FPGA, DPGA,Chameleon, XPUTER, etc. Reference is also made in particular in thiscontext to the following patents and patent applications of the sameapplicant: P 44 16 881.0-53, DE 197 81 412.3, DE 197 81 483.2, DE 196 54846.2-53, DE 196 54 593.5-53, DE 197 04 044.6-53, DE 198 80 129.7, DE198 61 088.2-53, DE 199 80 312.9, PCT/DE 00/01869, DE 100 36 627.9-33,DE 100 28 397.7, DE 101 10 530.4, DE 101 11 014.6, PCT/EP 00/10516, EP01 102 674.7, DE 196 51 075.9, DE 196 54 846.2, DE 196 54 593.5, DE 19704 728.9, DE 198 07 872.2, DE 101 39 170.6, DE 199 26 538.0, DE 101 42904.5, DE 101 10 530.4, DE 102 02 044.2, DE 102 06 857.7, DE 101 35210.7, EP 02 001 331.4, EP 01 129 923.7 as well as the particularparallel patent applications thereto. The entire disclosure of thesedocuments are incorporated herein by reference.

The above-mentioned architecture is used as an example to illustrate thepresent invention and is referred to hereinafter as VPU. Thearchitecture includes an arbitrary number of arithmetic, logic(including memory) and/or memory cells and/or networking cells and/orcommunication/peripheral (IO) cells (PAEs—Processing Array Elements),which may be positioned to form a unidimensional or multidimensionalmatrix (PA); the matrix may have different cells of any desiredconfiguration. Bus systems are also understood here as cells. Aconfiguration unit (CT) which affects the interconnection and functionof the PA is assigned to the entire matrix or parts thereof.

Memory access methods for reconfigurable modules which operate accordingto a DMA principle are described in German Patent No. P 44 16 881.0,where one or more DMAs are formed by configuration. In German PatentApplication No. 196 54 595.1, DMAs are fixedly implemented in theinterface modules and may be triggered by the PA or the CT.

German Patent Application No. DE 196 54 846.2 describes how internalmemories are written by external data streams and data is read out ofthe memory back into external units.

German Patent Application No. DE 199 26 538.0 describes expanded memoryconcepts according to DE 196 54 846.2 for achieving more efficient andeasier-to-program data transmission. U.S. Pat. No. 6,347,346 describes amemory system which corresponds in all essential points to German PatentApplication No. DE 196 54 846.2, having an explicit bus (global systemport) to a global memory. U.S. Pat. No. 6,341,318 describes a method fordecoupling external data streams from internal data processing by usinga double-buffer method, in which one buffer records/reads out theexternal data while another buffer records/reads out the internal data;as soon as the buffers are full/empty, depending on their function, thebuffers are switched, i.e., the buffer formerly responsible for theinternal data now sends its data to the periphery (or reads new datafrom the periphery) and the buffer formerly responsible for the externaldata now sends its data to the PA (reads new data from the PA). Thesedouble buffers are used in the application to buffer a cohesive dataarea.

Such double-buffer configurations have enormous disadvantages in thedata-stream area in particular, i.e., in data streaming, in which largevolumes of data streaming successively into a processor field or thelike must always be processed in the same way.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example reconfigurable processor.

FIG. 2 a shows a direct FIFO to PA coupling.

FIG. 2 b shows IO connected via RAM-PAEs.

FIG. 2 c shows FIFOs connected upstream from the IOs.

FIGS. 3 a-3 f show an example data processing method in a VPU.

FIGS. 4 a-4 e show another example data processing method in a VPU.

FIG. 5 shows an example embodiment of a PAE.

FIG. 6 shows an example of a wiring connection of ALU-PAEs and RAM-PAEsvia a bus system.

FIG. 7 a shows a circuit for writing data.

FIG. 7 b shows a circuit for reading data.

FIG. 8 shows an example connection between interface modules and/or PAEsto numerous and/or other data streams.

FIG. 9 shows an example sequence of a data read transfer via the circuitof FIG. 8.

FIG. 10 shows example shows example interface module connections withdata input and output via a collector, according to an exampleembodiment of the present invention.

FIG. 11 shows an example sequence of data transfer with a datacollector.

FIG. 12 shows a flow of data transfers for different applications,according to an example embodiment of the present invention.

FIG. 13 a shows a BURST-FIFO according to an example embodiment of thepresent invention.

FIG. 13 b shows a burst circuit according to an example embodiment ofthe present invention.

FIGS. 14 a-14 d show memory connections according to example embodimentsof the present invention.

FIG. 15 shows configuration couplings according to an example embodimentof the present invention.

DETAILED DESCRIPTION

An object of the present invention is to provide a novel approach forcommercial use.

A method according to an example embodiment of the present invention, incontrast to the previously known related art, allows a significantlysimpler means of controlling the buffers, i.e., memories, connected inbetween; the related art is disadvantageous in the core area of typicalapplications of reconfigurable processors in particular. External andinternal bus systems may be operated at different transfer rates and/orclock frequencies with no problem due to the memory devices connected inbetween because data is stored temporarily by the buffers. In comparisonwith inferior designs from the related art, this method requires fewermemory devices, typically only half as many buffers, i.e., data transferinterface memory devices, thus greatly reducing the hardware costs. Theestimated reduction in hardware costs amounts to 25% to 50%. It is alsosimpler to generate addresses and to program the configuration becausethe buffers are transparent for the programmer. Hardware is simpler towrite and to debug.

A paging method which buffers various data areas in particular fordifferent configurations may be integrated.

It should first be pointed out that various memory systems are known asinterfaces to the IO. Reference is made to German Patent No. and GermanPatent Application Nos. P 44 16 881.0, DE 196 54 595.1, and DE 199 26538.0. In addition, a method is described in German Patent ApplciationNo. DE 196 54 846.2 in which data is first loaded from the IO, (1) datais stored within a VPU after being computed, (2) the array (PA) isreconfigured, (3) data is read out from the internal memory and writtenback to another internal memory, (4) this is continued until the fullycomputed result is sent to the IO. Reconfiguration means, for example,that a function executed by a part of the field of reconfigurable unitsor the entire field and/or the data network and/or data and/or constantswhich are necessary in data processing is/are determined anew. Dependingon the application and/or embodiment, VPUs are reconfigured onlycompletely or also partially, for example. Different reconfigurationmethods are implementable, e.g., complete reconfiguration by switchingmemory areas (see, e.g., German Patent Application Nos. DE 196 51 075.9,DE 196 54 846.2) and/or wave reconfiguration (see, e.g., German PatentApplication-Nos. DE 198 07 872.2, DE 199 26 538.0, DE 100 28 397.7, DE102 06 857.7) and/or simple configuring of addressable configurationmemories (see, e.g., German Patent Application Nos. DE 196 51 075.9, DE196 54 846.2, DE 196 54 593.5). The entire disclosure of each of theparticular patent specifications is expressly incorporated herewith.

In one example embodiment, a VPU is entirely or partially configurableby wave reconfiguration or by directly setting addressable configurationmemories.

Thus, one of the main operating principles of VPU modules is to copydata back and forth between multiple memories, with additional andoptionally the same operations (e.g., long FIR filter) and/or otheroperations (e.g., FFT followed by Viterbi) being performed with the samedata during each copying operation. Depending on the particularapplication, data is read out from one or more memories and written intoone or more memories.

For storing data streams and/or states (triggers, see, e.g., GermanPatent Application Nos. DE 197 04 728.9, DE 199 26 538.0),internal/external memories (e.g., as FIFOs) are used and correspondingaddress generators are utilized. Any appropriate memory architecture maybe fixedly implemented specifically in the algorithm and/or flexiblyconfigured.

For performance reasons, the internal memories of the VPU are preferablyused, but basically external memories may also be used.

Assuming this, the following comments shall now be made regarding thebasic design:

Interface modules which communicate data between the bus systems of thePA and external units are assigned to an array (PA) (see, e.g., GermanPatent No. P 44 16 881.0, and German Patent Application No. DE 196 54595.1). Interface modules connect address buses and data buses in such away as to form a fixed allocation between addresses and data. Interfacemodules may preferably generate addresses or parts of addressesindependently.

Interface modules are assigned to FIFOs which decouple internal dataprocessing from external data transmission. A FIFO here is adata-streamable buffer, i.e., input/output data memory, which need notbe switched for data processing, in particular during execution of oneand the same configuration. If other data-streamable buffers are knownin addition to FIFO memories, they will subsequently also be covered bythe term where applicable. In particular, ring memories having one ormore pointers, in particular at least one write memory and one readmemory, should also be mentioned. Thus, for example, during multiplereconfiguration cycles for processing an application, the external datastream may be maintained as largely constant, regardless of internalprocessing cycles. FIFOs are able to store incoming/outgoing data and/oraddresses. FIFOs may be integrated into an interface module or assignedto one or more of them. Depending on the design, FIFOs may also beintegrated into the interface modules, and at the same time additionalFIFOs may be implemented separately. It is also possible to usedata-streamable buffers integrated into the module, e.g., by integrationof FIFO groups into a chip which forms a reconfigurable processor array.

In one example embodiment, multiplexers for free allocation of interfacemodules and FIFOs may also be present between the FIFOs (including thosethat are separate) and the interface modules. In one configuration, theconnection of FIFOs to external modules or internal parts of theprocessor field performed by a multiplexer may be specified based on theprocessor field, e.g., by the PAE sending and/or receiving data, but itmay also be determined, if desired, by a unit at a higher level of thehierarchy, such as a host processor in the case of division of dataprocessing into a highly parallel part of the task and a poorlyparallelizable part of the task and/or the multiplexer circuit may bedetermined by external specifications, which may be appropriate if, forexample, it is indicated with the data which type of data is involvedand how it is to be processed.

With regard to the external connection, units for protocol conversionbetween the internal and external bus protocols (e.g., RAMBUS, AMBA,PCI, etc.) are also provided. A plurality of different protocolconverters may also be used within one embodiment. The protocolconverters may be designed separately or integrated into the FIFOs orinterface modules.

In one possible embodiment, multiplexers for free assignment ofinterface modules/FIFOs and protocol converters may be provided betweenthe (separate) protocol converters and the interface modules/FIFOs.Downstream from the protocol converters there may be another multiplexerstage, so that a plurality of AMBA bus interfaces may be connected tothe same AMBA bus, for example. This multiplexer stage may also beformed, for example, by the property of an external bus of being able toaddress a plurality of units.

In one example embodiment, the circuit operates in master and slaveoperating modes. In the master mode, addresses and bus accesses aregenerated by the circuit and/or the assigned PA; in slave mode, externalunits access the circuit, i.e., the PA.

In other embodiments, additional buffer memories or data collectors maybe provided within the circuit, depending on the application, forexchanging data between interface modules. These buffer memoriespreferably operate in a random access mode and/or an MMU paging modeand/or a stack mode and may have their own address generators. Thebuffer memories are preferably designed as multi-port memories to permitsimultaneous access of a plurality of interface modules. It is possibleto access the buffer memories from a higher-level data processing unit,in particular from processors such as DSPs, CPUs, microcontrollers,etc., assigned to the reconfigurable module (VPU).

Now the decoupling of external data streams in particular will bedescribed. According to one aspect of the present invention, theexternal data streams are decoupled by FIFOs (input/output FIFO,combined as IO-FIFO) which are used between protocol converters andinterface modules.

The data processing method functions as follows: Through one or moreinput FIFOs, incoming data is decoupled from data processing in thearray (PA). Data processing may be performed in the following steps:

-   -   1. The input FIFO(s) is (are) read out, processed by the array        (PA) and/or written into one or more (other) memories (RAM        bank1) assigned locally to the array and/or preferably connected        laterally to the array. The lateral connection has the advantage        that the chip architecture and/or its design is/are simplified.    -   2. The array (PA) is reconfigured. The memories (e.g., RAM        bank1) are read out, data is processed and written into one or        more memories (e.g., RAM bank2 and/or RAM bank1) or, as an        alternative, data may already be written to the output FIFOs        according to step 4.    -   3. The array (PA) is reconfigured again and data is again        written into a memory.    -   4. This is continued until the result is sent to one or more        output FIFOs for output.    -   5. Then new data is again read out from the input FIFO(s) and        processed accordingly, i.e., data processing is continued in        step 1.

With the preferred design of the input/output FIFOs (IO-FIFOs) asmulti-ported FIFOs, data processing may be performed by protocolconverters simultaneously with writing into and/or reading out from theparticular FIFOs. The method described above yields a time decouplingwhich permits “quasi-steady-state” processing of constant data streamsin such a way that there is only a latency but no interruption in thedata stream when the first data packets have passed through. In anexpanded embodiment, the IO-FIFOs may be designed so that the number ofIO-FIFOs and their depth may be selected according to the application.In other words, IO-FIFOs may be distributed or combined (e.g., via atransmission gate, multiplexer/demultiplexer, etc.) so that there aremore IO-FIFOs or they are deeper. For example, 8 FIFOs of 1,024 wordseach may be implemented and configured so that 8 FIFOs of 1,024 words or2 FIFOs of 4,096 words are configured or, for example, 1 FIFO may beconfigured with 4,096 words and 4 with 1,024 words.

Modifications of the data processing method described here are possible,depending on the design of the system and the requirements of thealgorithms.

In an expanded embodiment, the FIFOs function in such a way that in thecase of output FIFOs the addresses belonging to the data inputs are alsostored in the FIFOs and/or input FIFOs are designed so that there is oneFIFO for the reading addresses to be sent out/already sent out and oneFIFO for the incoming data words assigned to the addresses.

Below is a discussion of how a FIFO-RAM bank coupling, which is possibleaccording to the present invention, may be implemented in a particularlypreferred variant of the present invention.

Depending on the application, it is possible to conduct the datatransfer with the IO-FIFOs via one or more additional memory stages (RAMbank) which are assigned locally to the array or are preferably coupledlaterally to the array and only then relay data to the data processingPAEs (e.g., ALU-PAEs described in, e.g., German Patent Appliation No. DE196 51 075.9).

In a preferred embodiment, RAM-PAEs have a plurality of data interfacesand address interfaces, they are thus designed as multi-port arrays.Designability of a data interface and/or address interface as a globalsystem port should also be mentioned as a possibility.

Additional memory stage(s) (RAM banks) may be implemented, for example,by memory modules corresponding to the RAM-PAEs, as described in, forexample, German Patent Application No. DE 196 54 846.2 and/or GermanPatent Application No. DE 199 26 538.0 and/or International PatentApplication No. PCT/EP 00/10516.

In other words, a RAM-PAE may constitute a passive memory which islimited (essentially) to the memory function (see, e.g., German PatentApplication No. DE 196 54 846.2) or an active memory which automaticallygenerates and controls functions such as address computation and/or busaccesses (see, e.g., German Patent Application No. DE 199 26 538.0). Inparticular, in one possible embodiment, active address generationfunctions and/or data transfer functions may also be implemented for a“global system port.” Depending on the design, active memories mayactively manage one or more data interfaces and address interfaces(active interfaces). Active interfaces may be implemented, for example,by additional modules such as sequencers/state machines and/or ALUsand/or registers, etc., within a RAM-PAE and/or by suitable hardwiringof an active interface to other PAEs whose function and networking areconfigured in one or more RAM-PAEs in accordance with the functions tobe implemented. Different RAM-PAEs may be assigned to different otherPAEs.

RAM-PAEs preferably have one or more of the following functions, i.e.,modes of operation: random access, FIFO, stack, cache, MMU paging. In apreferred embodiment, RAM-PAEs are connected via a bus to a higher-levelconfiguration unit (CT) and may be configured by it in their functionand/or interconnection and/or memory depth and/or mode of operation. Inaddition, there is preferably also the possibility of preloading andreading out the memory contents by the CT, for example, to set constantsand/or lookup tables (cos/sin).

Due to the use of multi-ported memories for the RAM-PAEs, writing and/orreading out of data into/from the IO-FIFOs and data access by the array(PA) may take place simultaneously, so that the RAM-PAEs may in turnagain have a buffer property, as described in German Patent ApplicationNo. DE 196 54 846.2, for example.

RAM-PAEs may be combined (as discussed in International PatentApplication No. PCT/EP 00/10516, for example) in such a way that largermemory blocks are formed and/or the RAM-PAEs operate so that thefunction of a larger memory is obtained (e.g., one 1,024-word RAM-PAEfrom two 512-word RAM-PAEs).

In an example embodiment, the units may be combined so that the sameaddress is sent to multiple memories. The address is subdivided so thatone portion addresses the entries in the memories and another portionindicates the number of the memory selected (SEL). Each memory has aunique number and may be selected unambiguously by comparing it withSEL. In a preferred embodiment, the number for each memory isconfigurable.

In another and/or additional example embodiment, an address is relayedfrom one memory to the next. This address is subdivided so that oneportion addresses the entries in the memories and another portionindicates the number (SEL) of the memory selected. This is modified eachtime data is relayed; for example, a 1 may be subtracted from this eachtime data is relayed. The memory in which this address part has acertain value (e.g., zero) is activated.

In an example embodiment, the units may be combined so that the sameaddress is sent to a plurality of memories. The address is subdivided sothat one part addresses the entries in the memories and another partindicates the number (SEL) of the memory selected. A bus runs betweenmemories, namely from one memory to the next, which has a referenceaddress such that the address has a certain value (e.g., zero) in thefirst memory and this value is modified each time data is relayed (e.g.,incremented by 1). Therefore, each memory has a different uniquereference address. The portion of the address having the number of theselected memory is compared with the reference address in each case. Ifthey are identical, the particular memory is selected. Depending on thedesign, the reference bus may be constructed using the ordinary data bussystem or a separated bus.

In an example embodiment, there may be an area check of the address partSEL to rule out faulty addressing.

It should now be pointed out that RAM-PAEs may be used as FIFOs. Thismay be preferred in particular when a comparatively large memorycapacity is provided by RAM-PAEs. Thus, in particular when usingmulti-ported memories for the RAM-PAEs, this yields the design option ofdispensing with explicit IO-FIFOs and/or configuring a correspondingnumber of RAM-PAEs as FIFOs in addition to the IO-FIFOs and sending datafrom the IO to the corresponding memory ports. This embodiment may beregarded as particularly cost efficient because no additional memoriesneed be provided, but instead the memories of the VPU architecture,which are configurable in their function and/or interconnection (see,e.g., German Patent Application No. DE 196 54 846.2, DE 199 26 538.0 andInternational Patent Application No. PCT/EP 00/10516), are configuredcorresponding to the character of configurable processors.

It is also possible to provide a multiplexer/demultiplexer upstreamand/or downstream from the FIFO. Incoming and/or outgoing data streamsmay be formed from one or more data records. For example, the followingfunction uses two incoming data streams (a and b) and one outgoing datastream (x):

function example (a, b : integer) -> x : integer for i:= 1 to 100   forj:= 1 to 100     x[i]:= a[i] * b[j].

This requirement may be met by using two approaches, for example:

-   a) The number of IO channels implemented is exactly equal to the    number of data streams required (see, e.g., German Patent No. P 44    16 881.0; German Patent Application No. DE 196 54 595.1); in the    stated function, for example, three I/O channels would thus be    necessary; or-   b) By using internal memories for decoupling data streams, more or    less as a register set (see, e.g., German Patent Application Nos. DE    199 26 538.0, DE 196 54 846.2). The different data streams are    exchanged between one or more memories and the IO (e.g., memory,    peripheral, etc.) by a time multiplex method, for example. Data may    then be exchanged internally in parallel with a plurality of    memories, if necessary, if the IO data is sorted (split) accordingly    during the transfer between these memories and the IO.

Approach a) is supported according to the present invention by makingavailable a sufficient number of IO channels and IO-FIFOs. However, thissimple approach is unsatisfactory because an algorithm-dependent andvery expensive number of IO channels, which cannot be determinedprecisely, must be made available.

Therefore, approach b) or a suitable combination of a) and b) may bepreferred, e.g., two IO channels, one input and one output, data streamsbeing multiplexed on each channel if necessary. It should be pointed outthat the interfaces should be capable of processing data streams, i.e.,a sufficiently high clock frequency and/or sufficiently short latenciesshould be provided on the internal and/or external buses. This may bethe reason why a combination of the two variants may be particularlypreferred, because by providing a plurality of parallel IO channels, therequired clocking of external and/or internal buses may be reducedaccordingly.

For approach b) or approaches based at least partially on approach b),it may be necessary to provide multiplexers and/or demultiplexers and toseparate the data streams of one data channel (e.g., a) and b) should beseparated from the input channel) or to combine a plurality of resultchannels on one output channel.

One or more multiplexers/demultiplexers (MuxDemux stage) may be locatedat different positions, depending on the technical hardwareimplementation and/or the functions to be executed. For example,

-   a) a MuxDemux stage may be connected between the input/output    interface (e.g., described in German Patent Application No. DE 196    54 595.1) and the FIFO stage (IO-FIFO and/or RAM-PAE as FIFO),-   b) a MuxDemux stage may be connected downstream from the FIFO stage    (IO-FIFO and/or RAM-PAE as FIFO), i.e., between the FIFO stage and    the PA,-   c) a MuxDemux stage may be connected between the IO-FIFO and the    RAM-PAEs.

The MuxDemux stage may in turn either be fixedly implemented in thehardware and/or formed by a suitable configuration of any PAEs designedaccordingly.

The position of the multiplexers/demultiplexers of the MuxDemux stage isdetermined by the configuration by a CT and/or the array (PA) and/or theIO itself, which may also be dynamically influenced, e.g., on the basisof the degree of filling of the FIFO(s) and/or on the basis of pendingdata transfers (arbitration).

In an example embodiment, the multiplexer/demultiplexer structure isformed by a configurable bus system (e.g., according to or resemblingthe bus system between the RAM/ALU/etc.—PAEs), whereby the bus systemmay in particular also be physically the same which is also used eitherby resource sharing or by a time multiplex method which may beimplemented through a suitable reconfiguration.

It may be particularly preferred if addresses are generated in aparticular manner, as is evident from the following discussion.Addresses for internal or external memories may be computed by addressgenerators. For example, groups of PAEs may be configured accordinglyand/or explicit address generators, implemented separately andspecially, if necessary (e.g., DMAs such as those described in GermanPatent No. DE 44 16 881) or within interface cells (such as thosedescribed in German Patent Application No. DE 196 54 595.1) may be used.In other words, either fixedly implemented address generators, which areintegrated into a VPU or are implemented externally, may be used and/orthe addresses may be calculated by a configuration of PAEs according tothe requirements of an algorithm.

Simple address generators are preferably fixedly implemented in theinterface modules and/or active memories (e.g., RAM-PAES). Forgeneration of complex address sequences (e.g., nonlinear,multidimensional, etc.), PAEs may be configured accordingly andconnected to the interface cells. Such methods having the correspondingconfigurations are described in International Patent Application No.PCT/EP 00/10516.

Configured address generators may belong to another configuration(ConfigID, see, e.g., German Patent Application Nos. DE 198 07 872.2, DE199 26 538.0 and DE 100 28 397.7) other than data processing. This makesa decoupling of address generation from data processing possible, sothat in a preferred method, for example, addresses may already begenerated and the corresponding data already loaded before or during thetime when the data processing configuration is being configured. Itshould be pointed out that such data preloading and/or addresspregeneration is particularly preferred for increasing processorperformance, in particular by reducing latency and/or the wait clockcycle. Accordingly, the result data and its addresses may still beprocessed during or after removal of the data processing/generatingconfiguration. In particular, it is possible through the use of memoriesand/or buffers such as the FIFOs described here, for example, to furtherdecouple data processing from memory access and/or IO access.

In a preferred procedure, it may be particularly effective to combinefixedly implemented address generators (HARD-AG) (see, e.g., GermanPatent Application No. DE 196 54 595.1) and configurable addressgenerators in the PA (SOFT-AG) in such a way that HARD-AGs are used forimplementation of simple addressing schemes, while complex addressingsequences are computed by the SOFT-AG and then sent to the HARD-AG. Inother words, individual address generators may overload and reset oneanother.

Interface modules for reconfigurable components are described in GermanPatent Application No. DE 196 54 595.1. The interface modules disclosedtherein and their operation could still be improved further to increaseprocessor efficiency and/or performance. Therefore, within the scope ofthe present invention, a particular embodiment of interface modules isproposed below such as that disclosed in particular in German PatentApplication No. DE 196 54 595.1.

Each interface module may have its own unique identifier (IOID) which istransmitted from/to a protocol converter and is used for assigning datatransfers to a certain interface module or for addressing a certaininterface module. The IOID is preferably CT-configurable.

For example, the IOID may be used to select a certain interface modulefor a data transfer in the case of accesses by an external master. Inaddition, the IOID may be used to assign the correct interface module toincoming read data. To do so, the IOID is, for example, transmitted withthe address of a data-read access to the IO-FIFOs and either storedthere and/or relayed further to the external bus. IO-FIFOs assign theIOIDs of the addresses sent out to the incoming read data and/or theIOIDs are also transmitted via the external bus and assigned by externaldevices or memories to the read data sent back.

IOIDs may then address the multiplexers (e.g., upstream from theinterface modules) so that they direct the incoming read data to thecorrect interface module.

Interface modules and/or protocol converters conventionally operate asbus masters. In a special embodiment, it is now proposed that interfacemodules and/or protocol converters shall function alternatively and/orfixedly and/or temporarily as bus slaves, in particular in a selectablemanner, e.g., in response to certain events, states of state machines inPAEs, requirements of a central configuration administration unit (CT),etc. In an additional embodiment, the interface modules are expanded sothat generated addresses, in particular addresses generated in SOFT-AGs,are assigned a certain data packet.

A preferred embodiment of an interface module is described below:

A preferred coupling of an interface module is accomplished byconnecting any PAEs (RAM, ALU, etc.) and/or the array (PA) via a bus(preferably configurable) to interface modules which are eitherconnected to the protocol converters or have the protocol convertersintegrated into them.

In a variant embodiment, IO-FIFOs are integrated into the interfacemodules.

For write access (the VPU sends data to external IOs, e.g.,memories/peripherals, etc.) it is advantageous to link the addressoutput to the data output, i.e., a data transfer takes place with the IOprecisely when a valid address word and a valid data word are applied atthe interface module, the two words may be originating from differentsources. Validity may be identified by a handshake protocol (RDY/ACK)according to German Patent Application Nos. DE 196 51 075.9 or DE 101 10530.4, for example. Through suitable logic gating (e.g., AND) of RDYsignals of address word and data word, the presence of two valid wordsis detectable, and IO access may be executed. On execution of the IOaccess, the data words and the address words may be acknowledged bygenerating a corresponding ACK for the two transfers. The IO accessincluding the address and data, as well as the associated statussignals, if necessary, may be decoupled in output FIFOs according to thepresent invention. Bus control signals are preferably generated in theprotocol converters.

For read access (the VPU receives data from external IOs, e.g.,memories/peripherals, etc.), the addresses for the access are firstgenerated by an address generator (HARD-AG and/or SOFT-AG) and theaddress transfer is executed. Read data may arrive in the same clockcycle or, at high frequencies, may arrive pipelined one or more clockcycles later. Both addresses and data may be decoupled through IO-FIFOs.

The conventional RDY/ACK protocol may be used for acknowledgment of thedata, and it may also be pipelined (see, e.g., German Patent ApplicationNos. DE 196 54 595.1, DE 197 04 742.4, DE 199 26 538.0, DE 100 28 397.7and DE 101 10 530.4).

The conventional RDY/ACK protocol may also be used for acknowledgment ofthe addresses. However, acknowledgment of the addresses by the receiverresults in a very long latency, which may have a negative effect on theperformance of VPUs. The latency may be bypassed in that the interfacemodule acknowledges receipt of the address and synchronizes the incomingdata assigned to the address with the address.

Acknowledgment and synchronization may be performed by any suitableacknowledgment circuit. Two possible embodiments are explained ingreater detail below, although in a non-limiting fashion:

a) FIFO

A FIFO stores the outgoing address cycles of the external bus transfers.With each incoming data word as a response to an external-bus access,the FIFO is instructed accordingly. Due to the FIFO character, thesequence of outgoing addresses corresponds to the sequence of outgoingdata words. The depth of the FIFO (i.e., the number of possible entries)is preferably adapted to the latency of the external system, so that anyoutgoing address may be acknowledged without latency and optimum datathroughput is achieved. Incoming data words are acknowledged accordingto the FIFO entry of the assigned address. If the FIFO is full, theexternal system is no longer able to accept any additional addresses andthe current outgoing address is not acknowledged and is thus held untildata words of a preceding bus transfer have been received and one FIFOentry has been removed. If the FIFO is empty, no valid bus transfer isexecuted and possibly incoming data words are not acknowledged.

b) Credit Counter

Each outgoing address of external bus transfers is acknowledged andadded to a counter (credit counter). Incoming data words as a responseto an external bus transfer are subtracted from the counter. If thecounter reaches a defined maximum value, the external system can nolonger accept any more addresses and the current outgoing address is notacknowledged and is thus held until data words of a preceding bustransfer have been received and the counter has been decremented. If thecounter content is zero, no valid bus transfer is executed and incomingdata words are not acknowledged.

To optimally support burst transfers, the method using a) (FIFO) isparticularly preferred, and in particular FIFOs may be used like theFIFOs described below for handling burst accesses and the assignment ofIOIDs to the read data.

The IO-FIFOs described here may be integrated into the interfacemodules. In particular, an IO-FIFO may also be used for embodimentvariant a).

The optional possibility of providing protocol converters is discussedabove. With regard to particularly advantageous possible embodiments ofprotocol converters, the following comments should be made:

A protocol converter is responsible for managing and controlling anexternal bus. The detailed structure and functioning of a protocolconverter depend on the design of the external bus. For example, an AMBAbus requires a protocol converter different from a RAMBUS. Differentprotocol converters are connectable to the interface modules, and withinone embodiment of a VPU, a plurality of, in particular, differentprotocol converters may be implemented.

In one preferred embodiment, the protocol converters are integrated intothe IO-FIFOs of the present invention.

It is possible according to the present invention to provide burst busaccess. Modern bus systems and SoC bus systems transmit large volumes ofdata via burst sequences. An address is first transmitted and data isthen transmitted exclusively for a number of cycles (see AMBASpecification 2.0, ARM Limited).

For correctly executing burst accesses, several tasks are to be carriedout:

1) Recognizing Burst Cycles

Linear bus accesses, which may be converted into bursts, must berecognized to trigger burst transfers on the external bus. Forrecognizing linear address sequences, a counter (TCOUNTER) may be used;it is first loaded with a first address of a first access and countslinearly up/down after each access. If the subsequent addresscorresponds to the counter content, there is a linear and burst-capablesequence.

2) Aborting at Boundaries

Some bus systems (e.g., AMBA) allow bursts (a) only up to a certainlength and/or (b) only up to certain address limits (e.g., 1024 addressblocks). For (a), a simple counter may be implemented according to thepresent invention, which counts from the first desired or necessary busaccess the number of data transmissions and at a certain-value whichcorresponds to the maximum length of the burst transfer, signals theboundary limits using a comparator, for example. For L(b), thecorresponding bit (e.g., the 10^(th) bit for 1024 address limits) whichrepresents the boundary limit may be compared between TCOUNTER and thecurrent address (e.g., by an XOR function). If the bit in the TCOUNTERis not equal to the bit in the current address, there has been atransfer beyond a boundary limit which is signaled accordingly.

3) Defining the Length

If the external bus system does not require any information regardingthe length of a burst cycle, it is possible and preferable according tothe present invention to perform burst transfers of an indefinite length(cf. AMBA). If length information is expected and/or certain burstlengths are predetermined, the following procedure may be used accordingto the present invention. Data and addresses to be transmitted arewritten into a FIFO, preferably with the joint use of the IO-FIFO, andare known on the basis of the number of addresses in the (IO-)FIFO. Forthe addresses, an address FIFO is used, transmitting in master mode theaddresses from the interface modules to the external bus and/oroperating conversely in slave mode. Data is written into a data FIFO,which transmits data according to the transmission (read/write). Inparticular, a different FIFO may be used for write transfers and forread transfers. The bus transfers may then be subdivided into fixedburst lengths, so that they are known before the individual bursttransfers and may be stated on initiation of the burst, burst transfersof the maximum burst length preferably being formed first and if thenumber of remaining (IO-)FIFO entries is smaller than the current burstlength, a next smaller burst length is used in each case. For example,ten (IO-;)FIFO entries may be transmitted at a maximum burst length of 4with 4, 4, 2 burst transfers.

4) Error Recovery

Many external bus systems (cf. AMBA) provide methods for errorelimination in which failed bus transfers are repeated, for example. Theinformation as to whether a bus transfer has failed is transmitted atthe end of a bus transfer, more or less as an acknowledgment for the bustransfer. To repeat a bus transfer, it is now necessary for all theaddresses to be available, and in the case of write access, the data tobe written away must also be available. According to the presentinvention, the address FIFOs (preferably the address FIFOs of theIO-FIFOs) are modified so that the read pointer is stored before eachburst transfer. Thus, a FIFO read pointer position memory means isprovided, in particular an address FIFO read pointer position memorymeans. This may form an integral part of the address FIFO in which, forexample, a flag is provided, indicating that information stored in theFIFO represents a read pointer position or it may be provided separatelyfrom the FIFO. As an alternative, a status indicating deletability couldalso be assigned to data stored in the FIFO, this status also beingstored and reset to “deletable” if successful data transmission has beenacknowledged. If an error has occurred, the read pointer is reset at theposition stored previously and the burst transfer is repeated. If noerror has occurred, the next burst transfer is executed and the readpointer is restored accordingly. To prevent the write pointer fromarriving at a current burst transfer and thus overwriting values whichmight still be needed in a repeat of the burst transfer, the full statusof the FIFOs is determined by comparing the stored read pointer with thewrite pointer.

IO-FIFOs and/or FIFOs for managing burst transfers may preferably beexpanded to incoming read data using the function of address assignment,which is known from the interface modules. Incoming read data may alsobe assigned the IOID which is preferably stored in the FIFOs togetherwith the addresses. Through the assignment of the IOID to incoming readdata, the assignment of the read data to the corresponding interfacemodules is possible by switching the multiplexers according to theIOIDs, for example.

According to the present invention, it is possible to use certain bussystems and/or to design bus systems in different ways. This isdescribed in further detail below. Depending on the design, differentbus systems may be used between the individual units, in particular theinterface modules, the IO-FIFOs, the protocol converters, and adifferent bus system may be implemented between each of two units.Different designs are implementable, the functions of a plurality ofdesigns being combinable within one design. A few design options aredescribed below.

The simplest possible design is a direct connection of two units.

In an expanded embodiment, multiplexers are provided between the units,which may have different designs. This example embodiment is preferredin particular when using a plurality of the particular units.

A multiplex function may be obtained using a configurable bus, which isconfigurable by a higher-level configuration unit (CT), specifically fora period of time for the connection of certain units.

In an example embodiment, the connections are defined by selectors whichdecode a portion of an address and/or an IOID, for example, bytriggering the multiplexers for the interconnection of the units. In aparticularly preferred embodiment, the selectors are designed in such away that a plurality of units may select a different unit at the sametime, each of the units being arbitrated for selection in chronologicalsequence. An example of a suitable bus system is described in, e.g.,German Patent Application No. DE 199 26 538.0.

Additional states may be used for arbitration. For example, datatransfers between the interface modules and the IO-FIFOs may beoptimized as follows:

In each case one block of a defined size of data to be transmitted iscombined within the FIFO stages. As soon as a block is full/empty, a busaccess is signaled to the arbiter for transmitting the data. Data istransmitted in a type of burst transfer, i.e., the entire data block istransmitted by the arbiter during a bus allocation phase. In otherwords, a bus allocation may take place in a manner determined by FIFOstates of the connected FIFOs, data blocks being used for thedetermination of state within a FIFO. If a FIFO is full, it mayarbitrate the bus for emptying; if a FIFO is empty, it may arbitrate thebus for filling. Additional states may be provided, e.g., in flush,which is used for emptying only partially full FIFOs and/or for fillingonly partially empty FIFOs. For example, flush may be used in a changeof configuration (reconfiguration).

In a preferred embodiment, the bus systems are designed as pipelines inorder to achieve high data transfer rates and clock rates by usingsuitable register stages and may also function as FIFOs themselves, forexample.

In a preferred embodiment, the multiplexer stage may also be designed asa pipeline.

According to the present invention, it is possible to connect aplurality of modules to one IO and to provide communication among themodules. In this regard, the following should be pointed out:

configuration modules which include a certain function and are reusableand/or relocatable within the PA are described in, for example, GermanPatent Application Nos. DE 198 07 872.2, DE 199 26 538.0, and DE 100 28397.7.

A plurality of these configuration modules may be configuredsimultaneously into the PA, dependently and/or independently of oneanother.

The configuration modules must be hardwired to a limited IO, which istypically provided in particular only at certain locations and istherefore not relocatable, in such a way that the configuration modulesare able to use the IOs simultaneously and data is assigned to thecorrect modules.

In addition, configuration modules that belong together (dependent) mustbe hardwired together in such a way that free relocation of theconfiguration modules is possible among one another in the PA.

Such a flexible design is in most cases not possible through theconventional networks (see, e.g., German Patent Nos. P 44 16 881.0, 02,03, 08), because this network must usually be explicitly allocated androuted through a router.

German Patent Application No. DE 197 04 742.4 describes a method ofconstructing flexible data channels within a PAE matrix according to thealgorithms to be executed so that a direct connection through and inaccordance with a data transmission is created and subsequentlydismantled again. Data to be transmitted may be precisely assigned toone source and/or one destination.

In addition and/or as an alternative to German Patent Application No. DE197 04 742.4 and the procedures and configurations described therein,additional possibilities are now provided through the present invention,and methods (hereinafter referred to jointly as GlobalTrack) that permitflexible allocation and interconnection during run time may be used,e.g., serial buses, parallel buses and fiber optics, each with suitableprotocols (e.g., Ethernet, Firewire, USB). Reference is made hereexplicitly to transmission by light using a light-conducting substrate,in particular with appropriate modulation for decoupling of thechannels. Another particular feature of the present invention withrespect to memory addressing, in particular paging and MMU options, isdescribed below.

Data channels of one or multiple GlobalTracks may be connected viamediating nodes to an ordinary network, e.g., according to German PatentNos. P 44 16 881.0, 02, 03, 08. Depending on the implementation, themediating nodes may be configured differently in the PA, e.g., assignedto each PAE, to a group and/or hierarchy of PAEs, and/or to every n^(th)PAE.

In a particularly preferred embodiment, all PAEs, interface modules,etc., have a dedicated connection to a GlobalTrack.

A configuration module is designed in such a way that it has access toone or a plurality of these mediating nodes.

A plurality of configuration modules among one another and/orconfiguration modules and IOs may now be connected via the GlobalTrack.With proper implementation (e.g., German Patent Application No. DE 19704 742.4) a plurality of connections may now be established and usedsimultaneously. The connection between transmitters and receivers may beestablished in an addressed manner to permit individual data transfer.In other words, transmitters and receivers are identifiable viaGlobalTrack. An unambiguous assignment of transmitted data is thuspossible.

Using an expanded IO, which also transmits the transmitter address andreceiver address—as is described in German Patent Application No. DE 10110 530.4, for example—and the multiplexing methods described in GermanPatent Application No. DE 196 54 595.1, data for different modules maybe transmitted via the IO and may also be assigned unambiguously.

In a preferred embodiment, data transfer is synchronized by handshakesignals, for example. In addition, data transfer may also be pipelined,i.e., via a plurality of registers implemented in the GlobalTrack orassigned to it. In a very complex design for large-scale VPUs or fortheir interconnection, a GlobalTrack may be designed in a networktopology using switches and routers; for example, Ethernet could beused.

It should be pointed out that different media may be used forGlobalTrack topologies, e.g., the method described in German PatentApplication No. DE 197 04 742.4 for VPU-internal connections andEthernet for connections among VPUs.

Memories (e.g., RAM-PAEs) may be equipped with an MMU-like pagingmethod. For example, a large external memory could then be broken downinto segments (pages), which in the case of data access within a segmentwould be loaded into one of the internal memories and, at a later pointin time, after termination of data access, would be written back intothe external memory.

In a preferred embodiment, addresses sent to a (internal) memory arebroken down into an address area, which is within the internal memory(MEMADR) (e.g., the lower 10 bits in a 1,024-entry memory) and a pageaddress (the bits above the lower 10). The size of a page is thusdetermined by MEMADR.

The page address is compared with a register (page register) assigned tothe internal memory. The register stores the value of the page addresslast transferred from a higher-level external (main) memory into theinternal memory.

If the page address matches the page register, free access to theinternal memory may take place. If the address does not match (pagefault), the current page content is written, preferably linearly, intothe external (main) memory at the location indicated by the pageregister.

The memory area in the external (main) memory (page) which begins at thelocation of the current new page address is written into the internalmemory.

In a particularly preferred embodiment, it is possible to specify byconfiguration whether or not, in the event of a page fault, the new pageis to be transferred from the external (main) memory into the internalmemory.

In a particularly preferred embodiment, it is possible to specify byconfiguration whether or not, in the event of a page fault, the old pageis to be transferred from the internal memory into the external (main)memory.

The comparison of the page address with the page register preferablytakes place within the particular memory. Data transfer control in theevent of page faults may be configured accordingly by any PAEs and/ormay take place via DMAs (e.g., in the interface modules or externalDMAs). In a particularly preferred embodiment, the internal memories aredesigned as active memories having integrated data transfer control(see, e.g., German Patent Application No. DE 199 26 538.0).

In another possible embodiment, an internal memory may have a plurality(p) of pages, the size of a page then preferably being equal to the sizeof the memory divided by p. A translation table (translation look-asidebuffer=TLB) which is preferably designed like a fully associative cachereplaces the page register and translates page addresses to addresses inthe internal memory; in other words, a virtual address may be translatedinto a physical address. If a page is not included in the translationtable (TLB), a page fault occurs. If the translation table has no roomfor new additional pages, pages may be transferred from the internalmemory into the external (main) memory and removed from the translationtable so that free space is again available in the internal memory.

It should be pointed out explicitly that a detailed discussion is notnecessary because a plurality of conventional MMU methods may be usedand may be used with only minor and obvious modifications.

The possibility of providing a collector memory, as it is known, hasbeen mentioned above. In this regard, the following details should alsobe mentioned.

A collector memory (collector) capable of storing larger volumes of datamay be connected between the interface modules and IO-FIFOs.

The collector may be used for exchanging data between the interfacemodules, i.e., between memories assigned to the array (e.g., RAM-PAEs).

The collector may be used as a buffer between data within areconfigurable module and external data.

A collector may function as a buffer for data between differentreconfiguration steps; for example, it may store data of differentconfigurations while different configurations are active and are beingconfigured. At deactivation of configurations, the collector storestheir data, and data of the newly configured and active configurationsis transmitted to the PA, e.g., to memories assigned to the array(RAM-PAEs).

A plurality of interface modules may have access to the collector andmay manage data in separate and/or jointly accessible memory areas.

In a preferred embodiment, the collector may have multiple terminals forinterface modules, which may be accessed simultaneously (i.e., it isdesigned as a multi-port collector device).

The collector has one or more terminals to an external memory and/orexternal peripherals. These terminals may be connected to the IO-FIFOsin particular.

In an expanded embodiment, processors assigned to the VPU, such as DSPs,CPUs and microcontrollers, may access the collector. This is preferablyaccomplished via another multi-port interface.

In a preferred embodiment, an address translation table is assigned tothe collector. Each interface may have its own address translation tableor all the interfaces may share one address translation table. Theaddress translation table may be managed by the PA and/or a CT and/or anexternal unit. The address translation table is used to assign collectormemory areas to any addresses and it operates like an MMU system. If anaddress area (page) is not present within the collector (pagemiss), thisaddress area may be loaded into the collector from an external memory.In addition, address areas (pages) may be written from the collectorinto the external memory.

For data transfer to or between the external memory, a DMA is preferablyused. A memory area within the collector may be indicated to the DMA forreading or writing transmission; the corresponding addresses in theexternal memory may be indicated separately or preferably removed by theDMA from the address translation table.

A collector and its address generators (e.g., DMAs) may preferablyoperate according to or like MMU systems, which are conventional forprocessors according to the related art. Addresses may be translated byusing translation tables (TLB) for access to the collector. According tothe present invention, all MMU embodiments and methods described forinternal memories may also be used on a collector. The operationalspecifics will not be discussed further here because they correspond toor closely resemble the related art.

In an expanded or preferred embodiment, a plurality of collectors may beimplemented.

According to the present invention, it is possible to optimize access tomemory. The following should be pointed out in this regard:

One basic property of the preferred reconfigurable VPU architecturePACT-XPP is the possibility of superimposing reconfiguration and dataprocessing (see, e.g., German Patent No. P 44 16 881.0, and GermanPatent Application Nos. DE 196 51 075.9, DE 196 54 846.2, DE 196 54593.5, DE 198 07 872.2, DE 199 26 538.0, DE 100 28 397.7, DE 102 06857.7). In other words, for example:

-   a) the next configuration may already be preloaded during data    processing; and/or-   b) data processing in other already-configured elements may already    begin while a number of configurable elements or certain    configurations are not yet configured or are in the process of being    configured; and/or-   c) the configuration of various activities is superimposed or    decoupled in such a way that they run with a mutual time offset at    optimum performance (see 8.1 address generation).

Modern memory protocols (e.g., SDRAM, DDRAM, RAMBUS) usually have thefollowing sequence or a sequence having a similar effect, but steps 2and 3 may possibly also occur in the opposite order:

1. Initializing access with the address given;

2. A long latency;

3. Rapid transmission of data blocks, usually as a burst.

This property may be utilized in a performance-efficient manner in VPUtechnology. For example, it is possible to separate the steps ofcomputation of the address(es), initialization of memory access, datatransfer and data processing in the array (PA) in such a way thatdifferent (chronological) configurations occur, so that largely optimumsuperpositioning of the memory cycles and data processing cycles may beachieved. Multiple steps may also be combined, depending on theapplication.

For example, the following method corresponds to this principle:

The application AP, which includes a plurality of configurations (ap=1,2, . . . , z), is to be executed. Furthermore, additionalapplications/configurations which are combined under WA are to beexecuted on the VPU:

1. Read addresses are first computed (in an ap configuration of AP) andthe data transfers and IO-FIFOs are initialized;

2. Data transmitted for AP and now present in IO-FIFOs is processed (inan (ap+1) configuration) and, if necessary, stored in FIFOs, buffers orintermediate memories, etc.;

2a. Computation of results may require a plurality of configurationcycles (n) at the end of which the results are stored in an IO-FIFO, and

3. The addresses of the results are computed and the data transfer isinitialized; this may take place in parallel or later in the sameconfiguration or in an (ap+n+2) configuration; at the same time or witha time offset, data is then written from the IO-FIFOs into the memories.

Between the steps, any configuration from WA may be executed, e.g., whena waiting time is necessary between steps, because data is not yetavailable.

Likewise, in parallel with the processing of AP, configurations from WAmay be executed during the steps, e.g., if AP does not use the resourcesrequired for WA.

It will be self-evident to those skilled in the art that variouslymodified embodiments of this method are also possible.

In one possible embodiment, the processing method may take place asshown below (Z marks a configuration cycle, i.e., a unit of time):

Other configurations Z Configuration AP (WA) 1 Compute read addresses,Any other initialize access configurations 2 Input of data and/or data3 + k Process data processing, read/ (if necessary in a plurality ofwrite processes (k) configuration cycles) using IO-FIFOs 4 + k Computewrite addresses, and/or RAM-PAEs in initialize access other resources or5 + k Output of data time-multiplexed resources via configuration cycles

This sequence may be utilized efficiently by the data processing methoddescribed in, for example, German Patent Application No. DE 102 02 044.2in particular.

The methods and devices described above are preferably operated usingspecial compilers, which are expanded in particular in comparison withtraditional compilers. The following should be pointed out in thisregard:

For generating configurations, compilers that run on any computer systemare used. Typical compilers include, for example, C-compilers and/oreven NML compilers for VPU technology, for example. Particularlysuitable compiler methods are described in German Patent ApplicationNos. DE 101 39 170.6, and DE 101 29 237.6, and European Patent No. EP 02001 331.4, for example.

The compiler, at least partially, preferably takes into account thefollowing particular factors: Separation of addressing into

-   -   1. external addressing, i.e., data transfers with external        modules,    -   2. internal addressing, i.e., data transfers among PAEs, in        particular between RAM-PAEs and ALU-PAEs,    -   3. in addition, time decoupling also deserves special attention.

Bus transfers are broken down into internal and external transfers.

bt1) External read accesses are separated and, in one possibleembodiment, they are also translated into a separate configuration. Datais transmitted from an external memory to an internal memory.

bt2) Internal accesses are coupled to data processing, i.e., internalmemories are read and/or written for data processing.

bt3) External write accesses are separated and, in one possibleembodiment, they are also translated into a separate configuration. Datais transmitted from an internal memory into an external memory.

bt1, bt2, and bt3 may be translated into different configurations whichmay, if necessary, be executed at a different point in time.

This method will now be illustrated on the basis of the followingexample:

function example (a, b:integer)->x:integer

for i := 1 to 100   for j := 1 to 100     x[i] := a[i] * b[j].

This function is transformed by the compiler into three parts, i.e.,configurations (subconfig):

example#dload: Loads data from externally (memories, peripherals, etc.)and writes it into internal memories. Internal memories are indicated byr# and the name of the original variable.

example#process: Corresponds to the actual data processing. This readsdata out of internal operands and writes the results back into internalmemories.

example#dstore: Writes the results from the internal memory intoexternally (memories, peripherals, etc.).

function example# (a, b : integer) -> x : integer subconfigexample#dload for i := 1 to 100   r#a[i] := a[i] for j := 1 to 100  r#b[j] := b[j] subconfig example#process for i := 1 to 100   for j :=1 to 100     r#x[i] := r#a[i] * r#b[j] subconfig example#dstore for i :=1 to 100   x[i] := r#x[i].

An effect of the example method is that instead of i*j=100*100=10,000external accesses, only i+j=100+100=200 external accesses are performedfor reading the operands. These accesses are also completely linear,which greatly accelerates the transfer rate in modern bus systems(burst) and/or memories (SDRAM, DDRAM, RAMBUS, etc.).

Internal memory accesses take place in parallel, because differentmemories have been assigned to the operands.

For writing the results, i=100 external accesses are necessary and mayagain be performed linearly at maximum performance.

If the number of data transfers is not known in advance (e.g., WHILEloop) or is very large, a method may be used which reloads the operandsas necessary through subprogram call instructions and/or writes theresults externally. In a preferred embodiment, the states of the FIFOsmay (also) be queried: “empty” if the FIFO is empty and “full” if theFIFO is full. The program flow responds according to the states. Itshould be pointed out that certain variables (e.g., ai, bi, xi) aredefined globally. For performance optimization, a scheduler may executethe configurations example#dloada, example#dloadb before calling upexample#process according to the methods already described, so that datais already preloaded. Likewise, example#dstore(n) may still be called upafter termination of example#process in order to empty r#x.

subconfig example#dloada(n)   while  !full(r#a) AND ai <= n     r#a[ai]:= a[ai]     ai++ subconfig example#dloadb(n)   while !full(r#b) AND bi<= n     r#b[bi] := b[bi]     bi++ subconfig example#dstore (n)   while!empty(r#x) AND xi <= n     x[xi] := r#x[xi]     xi++ subconfigexample#process for i := 1 to n   for j := 1 to m     if empty(r#a) thenexample#dloada(n)     if empty(r#b) then example#dloadb(m)     iffull(r#x) then example#dstore(n)     r#x[i] := r#a[i] + r#b[j]   bj :=1.

The subprogram call instructions and managing of the global variablesare comparatively complex for reconfigurable architectures. Therefore,in a preferred embodiment, the following optimization may be performed;in this optimized method, all configurations are run largelyindependently and are terminated after being completely processed(terminate). Since data b[j] is required repeatedly, example#dloadb mustaccordingly be run through repeatedly. To do so, for example, twoalternatives will be described:

Alternative 1: example#dloadb terminates after each run-through and isreconfigured for each new start by example#process.

Alternative 2: example#dloadb runs infinitely and is terminated byexample#process.

While “idle,” a configuration is inactive (waiting).

subconfig example#dloada(n) for i := 1 to n   while full(r#a)    idle   r#a[i] :=a[i]   terminate subconfig example#dloadb(n) while 1 //ALTERNATIVE 2   for i := 1 to n     while full(r#b)      idle     r#b[i]:= a[i]   terminate subconfig example#dstore(n)  for i := 1 to n   whileempty(r#b)     idle   x[i] := r#x[i]  terminate subconfigexample#process for i := 1 to n   for j := 1 to m     while empty(r#a)or empty(r#b) or full(r#x)      idle   r#x[i] := r#a[i] * r#b[j] configexample#dloadb(n) // ALTERNATIVE 1 terminate example#dloadb(n) //ALTERNATIVE 2 terminate

To avoid waiting cycles, configurations may also be terminated as soonas they are temporarily no longer able to continue fulfilling theirfunction. The corresponding configuration is removed from thereconfigurable module but remains in the scheduler. Therefore, the“reenter” instruction is used for this below. The relevant variables aresaved before termination and are restored when configuration isrepeated:

subconfig example#dloada(n) for ai := 1 to n   if full(r#a) reenter  r#a[ai] := a[ai] terminate subconfig example#dloadb(n) while 1 //ALTERNATIVE 2   for bi := 1 to n     if full(r#b) reenter     r#b[bi] :=a[bi] terminate subconfig example#dstore(n)   for xi := 1 to n     ifempty(r#b) reenter     x[xi] := r#x[xi] terminate subconfigexample#process for i := 1 to n   for j := 1 to m     if empty(r#a) orempty(r#b) or full(r#x) reenter     r#x[i] := r#a[i] * r#b[j] configexample#dloadb(n) // ALTERNATIVE 1 terminate example#dloadb(n) //ALTERNATIVE 2 terminate

With regard to the preceding discussion and to the following, thepossibility of using a ‘context switch’ according to the presentinvention should also be pointed out. In this regard, the followingshould be noted:

Repeated start of configurations, e.g., “reenter,” requires that localdata (e.g., ai, bi, xi) be backed up and restored. Known related-artmethods provide explicit interfaces to memories or to a CT to transmitdata. All of these methods may be inconsistent and/or may requireadditional hardware.

The context switch according to the present invention is implemented insuch a way that a first configuration is removed; data to be backed upremains in the corresponding memories (REGs) (memories, registers,counters, etc.).

A second configuration is loaded; this connects the REGs in a suitablemanner and in a defined sequence to one or multiple global memory(memories).

The configuration may use address generators, for example, to access theglobal memory (memories).

The configuration may use address generators, for example, to accessREGs designed as memories.

According to the configured connection between the REGs, the contents ofthe REGs are written into the global memory in a defined sequence, theparticular addresses being predetermined by address generators. Theaddress generator generates the addresses for the global memory(memories) in such a way that the memory areas (PUSHAREA) that have beenwritten are unambiguously assigned to the first configuration removed.

In other words, different address areas are preferably provided fordifferent configurations.

The configuration corresponds to a PUSH of ordinary processors.

Other configurations subsequently use the resources.

The first configuration is to be started again, but first a thirdconfiguration which connects the REGs of the first configuration in adefined sequence is started.

The configuration may use address generators, for example, to access theglobal memory or memories. The configuration may use address generators,for example, to access REGs designed as memories.

An address generator generates addresses, so that correct access to thePUSHAREA assigned to the first configuration takes place. The generatedaddresses and the configured sequence of the REGs are such that data ofthe REGs is written from the memories into the REGs in the originalorder. The configuration corresponds to a POP of ordinary processors.

The first configuration is restarted.

In summary, a context switch is implemented in such a way that data tobe backed up is exchanged with a global memory by loading particularconfigurations which operate like processor architectures known fromPUSH/POP.

There is also the possibility of providing a special task switch and/ormulticonfiguration handling.

In a preferred mode of operation, different data blocks of differentconfigurations may be partitioned. These partitions may be accessed in atime-optimized manner by preloading a portion of the operands of asubsequent configuration P from external (main) memories and/or other(peripheral) data streams into the internal memories, e.g., duringexecution of a configuration Q, and during the execution of P, theresults of Q as a portion of the total result from the internal memoriesare written into external (main) memories and/or other (peripheral) datastreams.

The functioning here differs considerably from that described in, forexample, U.S. Pat. No. 6,341,318. A data stream or data block ispreferably decoupled by a FIFO structure (e.g., IO-FIFO). Different datastreams or data blocks of different configurations in particular arepreferably decoupled by different memories and/or FIFO areas and/orassignment marks in the FIFOs.

The optional MMU methods described above may be used for decoupling andbuffering external data. In one type of application, a large externaldata block may be broken down into a plurality of segments, each may beprocessed within a VPU.

In an additional preferred mode of operation, different data blocks ofdifferent configurations may be broken down into partitions according tothe method described above, these partitions now being defined as pagesfor an MMU. In this way, time-optimized access is possible by preloadingthe operands of a subsequent configuration P as a page from external(main) memories and/or other (peripheral) data streams into the internalmemories, e.g., during execution of a configuration Q in the PA, andduring the execution of P, the results of Q as a page from the internalmemories are written into external (main) memories and/or other(peripheral) data streams.

For the methods described above, preferably internal memories capable ofmanaging a plurality of partitions and/or pages are used.

These methods may be used for RAM-PAEs and/or collector memories.

Memories having a plurality of bus interfaces (multi-port) arepreferably used to permit simultaneous access of MMUs and/or the PAand/or additional address generators/data transfer devices.

In one embodiment, identifiers are also transmitted in the datatransfers, permitting an assignment of data to a resource and/or anapplication. For example, the method described in German PatentApplication No. DE 101 10 530.4 may be used. Different identifiers mayalso be used simnultaneously.

In a particularly preferred embodiment, an application identifier (APID)is also transmitted in each data transfer along with the addressesand/or data. An application includes a plurality of configurations. Onthe basis of the APID, the transmitted data is assigned to anapplication and/or to the memories or other resources (e.g., PAEs,buses, etc.) intended for an application. To this end, the APIDs may beused in different ways.

Interface modules, for example, may be selected by APIDs accordingly.

Memories, for example, may be selected by APIDs accordingly.

PAEs, for example, may be selected by APIDs accordingly.

For example, memory segments in internal memories (e.g., RAM-PAEs,collector(s)) may be assigned by APIDs. To do so, the APIDS, like anaddress part, may be entered into a TLB assigned to an internal memoryso that a certain memory area (page) is assigned and selected as afunction of an APID.

This method yields the possibility of efficiently managing and accessingdata of different applications within a VPU.

There is the option of explicitly deleting data of certain APIDs(APID-DEL) and/or writing into external (main) memories and/or other(peripheral) data streams (APID-FLUSH). This may take place whenever anapplication is terminated. APID-DEL and/or APID-FLUSH may be triggeredby a configuration and/or by a higher-level loading unit (CT) and/orexternally.

The following processing example is presented to illustrate the method.

An application Q (e.g., APID=Q) may include a configuration for readingoperands (e.g., ConfigID=j), a configuration for processing operands(e.g., ConfigID=w), and a configuration for writing results (e.g.,ConfigID=s).

Configuration j is executed first to read the operands chronologicallyoptimally decoupled. Configurations of other applications may beexecuted simultaneously. The operands are written from external (main)memories and/or (peripheral) data streams into certain internal memoriesand/or memory areas according to the APID identifier.

Configuration w is executed to process the stored operands. To do so,the corresponding operands in the internal memories and/or memory areasare accessed by citation of APIDs. Results are written into internalmemories and/or memory areas accordingly by citation of APIDs.Configurations of other applications may be executed simultaneously. Inconclusion, configuration s writes the stored results from the internalmemories and/or memory areas into external (main) memories and/or other(peripheral) data streams. Configurations of other applications may beexecuted simultaneously.

To this extent, the basic sequence of the method corresponds to thatdescribed above for optimization of memory access.

If data for a certain APID is not present in the memories or if there isno longer any free memory space for this data, a page fault may betriggered for transmission of the data.

While a module was initially assumed in which a field of reconfigurableelements is provided having little additional wiring, such as memories,FIFOs, and the like, it is also possible to use the ideas according tothe present invention for systems known as “systems on a chip” (SoC).For SoCs the terms “internal” and “external” are not completelyapplicable in the traditional terminology, e.g., when a VPU is linked toother modules (e.g., peripherals, other processors, and in particularmemories) on a single chip. The following definition of terms may thenapply; this should not be interpreted as restricting the scope of theinvention but instead is given only as an example of how the ideas ofthe present invention may be applied with no problem to constructs whichtraditionally use a different terminology:

internal: within a VPU architecture and/or areas belonging to the VPUarchitecture and IP,

external: outside of a VPU architecture, i.e., all other modules, e.g.,peripherals, other processors, and in particular memories on a SoCand/or outside the chip in which the VPU architecture is located.

A preferred embodiment will now be described.

In a particularly preferred embodiment, data processing PAEs are locatedand connected locally in the PA (e.g., ALUs, logic, etc.). RAM-PAEs maybe incorporated locally into the PA, but in a particularly preferredembodiment they are remote from the PA or are placed at its edges (see,e.g., German Patent Application No. DE 100 50 442.6). This takes placeso as not to interfere with the homogeneity of the PA in the case oflarge RAM-PAE memories, where the space required is much greater thanwith ALU-PAEs and because of a gate/transistor layout (e.g., GDS2) ofmemory cells, which usually varies greatly. If the RAM-PAEs havededicated connections to an external bus system (e.g., global bus), theyare preferably located at the edges of a PA for reasons of layout, floorplan, and manufacturing.

The configurable bus system of the PA is typically used for the physicalconnection.

In an expanded embodiment, PAEs and interface modules, as well asadditional configurable modules, if necessary, have a dedicatedconnection to a dedicated global bus, e.g., a GlobalTrack.

Interface modules and in particular protocol converters are preferablyremote from the PA and are placed outside of its configuration. Thistakes place so as not to interfere with the homogeneity of the PA andbecause of a gate/transistor layout (e.g., GDS2) of the interfacemodules/protocol converters, which usually varies greatly. In addition,the connections to external units are preferably placed at the edges ofa PA for reasons of layout, floor plan, and manufacturing. The interfacemodules are preferably connected to the PA by the configurable bussystem of the PA, the interface modules being connected to its outeredges. The bus system allows data exchange to take place configurablybetween interface modules and any PAEs within the PA. In other words,within one or different configurations, some interface modules may beconnected to RAM-PAEs, for example, while other interface modules may beconnected to ALU-PAEs, for example.

The IO-FIFOs are preferably integrated into the protocol converter. Topermit a greater flexibility in the assignment of the internal datastreams to the external data streams, the interface modules and protocolconverters are designed separately and are connected via a configurablebus system.

The present invention is explained in greater detail below only as anexample and in a nonrestrictive manner with reference to the drawings.

FIG. 1 shows a particularly preferred design of a reconfigurableprocessor which includes a core (array PA) (0103) including, forexample, a configuration of ALU-PAEs (0101) (for performingcomputations) and RAM-PAEs (0102) (for saving data) and thus correspondsto the basic principle described in, for example, German PatentApplication No. DE 196 54 846.2. The RAM-PAEs are preferably notintegrated locally into the core, but instead are remote from theALU-PAEs at the edges of or outside the core. This takes place so as notto interfere with the homogeneity of the PA in the case of large RAM-PAEmemories where the space requirement is far greater than that ofALU-PAEs and because of a gate/transistor layout (e.g., GDS2) of memorycells which usually varies greatly. If the RAM-PAEs have dedicatedconnections to an external bus system (e.g., dedicated global bus;GlobalTrack; etc.), then they are preferably placed at the edges of a PAfor reasons of layout, floor plan, and manufacturing.

The individual units are interlinked via bus systems (0104). Interfacemodules (interface modules and protocol converters, if necessary) (0105)are located at the edges of the core and are connected to external buses(IO), as similarly described in German Patent Application No. DE 196 54595.1. The interface modules may have different designs, depending onthe implementation, and may fulfill one or more of the followingfunctions, for example:

-   -   1. Combining and synchronizing a plurality of bus systems to        synchronize addresses and data for example,    -   2. Address generators and/or DMAs,    -   3. FIFO stages for decoupling data and/or addresses,    -   4. Interface controllers (e.g., for AMBA bus, RAMBUS, RapidIO,        USB, DDRRAM, etc.).

FIG. 2 shows a different embodiment of the architecture according to thepresent invention, depicting a configuration 0201 of ALU-PAEs (PA)linked to a plurality of RAM-PAEs (0202). External buses (IOs) (0204)are connected via FIFOs (0203).

FIG. 2 a shows a direct FIFO to PA coupling.

FIG. 2 b shows the IO (0204) connected to 0201 via the RAM-PAEs (0202).The connection occurs typically via the configurable bus system 0104 ora dedicated bus system. Multiplexers/demultiplexers (0205) switch aplurality of buses (0104) to the IOs (0204). The multiplexers aretriggered by a configuration logic and/or address selector logic and/oran arbiter (0206). The multiplexers may also be triggered through thePA.

FIG. 2 c corresponds to FIG. 2 b, but FIFOs (0203) have been connectedupstream from the IOs.

The diagrams in FIG. 3 correspond to those in FIG. 2, which is why thesame reference numbers are used. FIG. 3 illustrates the preferred dataprocessing method in a VPU. FIG. 3 a: data passes through the IO (0204)into an input FIFO (0303 corresponding to 0203) and is loaded from thisinto the PA (0201) and/or beforehand into memory 0202.

FIGS. 3 b-e show the data execution in which data is transmitted betweenthe memories. During this period of time, the FIFOs may still transmitinput data (0301) and/or output data (0302).

In FIG. 3 f, data is loaded from the PA and/or from the memories intothe output FIFO (0304).

It should be pointed out again that input of data from the input FIFOinto the RAM-PAEs or 0201 and writing of data from 0201 or the RAM-PAEsmay take place simultaneously.

It should likewise be pointed out that the input/output FIFOs are ableto receive and/or send external data continuously during steps a-f.

FIG. 4 shows the same method in a slightly modified version in whichmultiplexers/demultiplexers (0401) are connected between the FIFOs and0201 for simple data distribution. The multiplexers are triggered by aconfiguration logic and/or address selector logic and/or an arbiter(0402).

Multiple configurations take place for data processing (a-e).

The data may be read into memories and/or directly (0403) into the PAfrom the FIFOs (input FIFOs). During the input operation, data may bewritten from the PA and/or memories into FIFOs (output FIFOS) (0404).For data output, data may be written from the memories and/or directly(0405) from the PA into the FIFOs. Meanwhile, new data may be writtenfrom the input FIFOs into memories and/or the PA (0406).

New data (0407) may already be entered during a last configuration, forexample.

During the entire processing, data may be transmitted from externallyinto the input FIFOs (0408) and/or from the output FIFOs to externally(0409).

FIG. 5 shows a possible embodiment of a PAE. A first bus system (0104 a)is connected to a data processing unit (0501), the results of which aretransmitted to a second bus system (0104 b). The vertical data transferis carried over two register/multiplexer stages (FREG 0502, BREG 0503),each with a different transfer direction. Preferably simple ALUs, e.g.,for addition, subtraction, and multiplex operations, may be integratedinto the FREG/BREG. The unit is configured in its function andinterconnection by a configuration unit (CT) via an additional interface(0504). In a preferred embodiment, there is the possibility of settingconstants in registers and/or memories for data processing. In anotherembodiment, a configuration unit (CT) may read out data from the workingregisters and/or memories.

In an expanded embodiment, a PAE may additionally have a connection to adedicated global bus (0505) (e.g., a GlobalTrack) and may thuscommunicate directly with a global, and if necessary also an externalmemory and/or peripheral unit, for example. In addition, a global busmay be designed so that different PAEs may communicate directly with oneanother via this bus, and in a preferred embodiment they may alsocommunicate with modules for an external connection (e.g., interfacemodules). A bus system such as that described in German PatentApplication No. DE 197 04 742.4, for example, may be used for suchpurposes.

The data processing unit (0501) may be designed for ALU-PAEs as anarithmetic logic unit (ALU), for example. Different ALU-PAEs may usedifferent ALUs and bus connection systems. One ALU may have more thantwo bus connections to 0104 a and/or 0104 b, for example.

The data processing unit (0501) may be designed as a memory forRAM-PAEs, for example. Different RAM-PAEs may use different memories andbus connection systems. For example, a memory may have a plurality, inparticular, more than two bus connections to 0104 a and/or 0104 b toallow access of a plurality of senders/receivers to one memory, forexample. Accesses may preferably also take place simultaneously(multi-port).

The function of the memory includes, for example, the followingfunctions or combinations thereof: random access, FIFO, stack, cache,page memory with MMU method.

In addition, in a preferred embodiment, the memory may be preloaded withdata from the CT (e.g., constants, lookup tables, etc.). Likewise, in anexpanded embodiment, the CT may read back data from the memory via 0504(e.g., for debugging or for changing tasks).

In another embodiment, the RAM-PAE may have a dedicated connection(0505) to a global bus. The global bus connects a plurality of PAEsamong one another and in a preferred embodiment also to modules for anexternal connection (e.g., interface modules). The system described inGerman Patent Application No. DE 197 04 742.4 may be used for such a bussystem.

RAM-PAEs may be wired together in such a way that an n-fold largermemory is created from a plurality (n) of RAM-PAEs.

FIG. 6 shows an example of a wiring connection of ALU-PAEs (0601) andRAM-PAEs (0602) via a bus system 0104. FIG. 1 shows a preferred exampleof a wiring connection for a reconfigurable processor.

FIG. 7 shows a simple embodiment variant of an IO circuit correspondingto 0105. Addresses (ADR) and data (DTA) are transmitted together withsynchronization lines (RDY/ACK) between the internal bus systems (0104)and an external bus system (0703). The external bus system leads toIO-FIFOs and/or protocol converters, for example.

FIG. 7 a shows a circuit for writing data. The addresses and dataarriving from 0104 are linked together (0701). A FIFO stage fordecoupling may be provided between 0104 and 0703 in the interfacecircuit (0701).

FIG. 7 b shows a circuit for reading data, in which an acknowledgmentcircuit (0702, e.g., FIFO, counter) is provided for coordinating theoutgoing addresses with the incoming data. In 0701 a and/or in 0701 b, aFIFO stage for decoupling may be provided between 0104 and 0703. If aFIFO stage is provided in 0701 b, it may also be used for acknowledgmentcircuit 0702.

FIG. 8 shows a possible connection structure between interface modulesand/or PAEs having a dedicated global bus (0801) and protocol converters(0802) to external (main) memories and/or other (peripheral) datastreams. Interface modules are connected (0803) to a PA, preferably viatheir network according to 0104.

A bus system (0804 a, 0804 b) is provided between interface modulesand/or PAEs having a dedicated global bus (0801) and protocol converters(0802). In a preferred embodiment, 0804 is able to transmit pipelineddata over a plurality of register stages. 0804 a and 0804 b areinterconnected via switches (e.g., 0805) which are designed astransmission gates and/or tristate buffers and/or multiplexers, forexample. The multiplexers are triggered by rows and columns. Triggeringunits (0806) control the data transfer of the interface modules and/orPAEs having a dedicated global bus (0801) to the protocol converters(0802), i.e., in the transfer direction 0804 a to 0804 b. Triggeringunits (0807) control the data transfer of the protocol converters (0802)to the interface modules and/or the PAEs having a dedicated global bus(0801), i.e., in the transfer direction 0804 b to 0804 a. The triggeringunits (0806) each decode address areas for selection of the protocolconverters (0802); the triggering units (0807) each decode IOIDs forselection of the interface modules and/or PAEs having a dedicated globalbus (0801).

Triggering units may operate according to different types of triggering,e.g., fixed connection without decoding; decoding of addresses and/orIOIDs; decoding of addresses and/or IOIDs and arbitration. One ormultiple data words/address words may be transmitted per arbitration.Arbitration may be performed according to different rules. The interfacemodules may preferably have a small FIFO for addresses and/or data inthe output direction and/or input direction. A particular arbitrationrule preferably arbitrates an interface module having a FULL FIFO or anEMPTY FIFO or a FIFO to be emptied (FLUSH), for example.

Triggering units may be designed as described in German PatentApplication No. DE 199 26 538.0 (FIG. 32), for example. These triggeringunits may be used for 0807 or 0806. When used as 0806, 0812 correspondsto 0804 a, and 0813 corresponds to 0804 b. When used as 0807, 0812corresponds to 0804 b, and 0813 corresponds to 0804 a. Decoders (0810)decode the addresses/IOIDs of the incoming buses (0812) and trigger anarbiter (0811), which in turn switches the incoming buses to an outputbus (0813) via a multiplexer.

The protocol converters are coupled to external bus systems (0808), aplurality of protocol converters optionally being connected to the samebus system (0809), so that they are able to utilize the same externalresources.

The IO-FIFOs are preferably integrated into the protocol converters, aFIFO (BURST-FIFO) for controlling burst transfers for the external buses(0808) being connected downstream from them if necessary. In a preferredembodiment, an additional FIFO stage (SYNC-FIFO) for synchronizing theoutgoing addresses with the incoming data is connected downstream fromthe FIFOs.

Various programmable/configurable FIFO structures are depicted in0820-0823, where A indicates the direction of travel of an address FIFO,D indicates the direction of travel of a data FIFO. The direction ofdata transmission of the FIFOs depends on the direction of datatransmission and the mode of operation. If a VPU is operating as a busmaster, then data and addresses are transmitted from internally to theexternal bus in the event of a write access (0820), and in the event ofa read access (0821) addresses are transmitted from internally toexternally and data from externally to internally.

If a VPU is operating as a bus slave, then data and addresses aretransmitted from the external bus to internally in the event of a writeaccess (0822) and in the event of a read access (0823) addresses aretransmitted from externally to internally and data is transmitted frominternally to externally.

In all data transfers, addresses and/or data and/or IOIDs and/or APIDsmay be assigned and also stored in the FIFO stages.

In a particularly preferred embodiment, the transfer rate (operatingfrequency) of the bus systems 0104, 0804, and 0808/0809 may each bedifferent due to the decoupling of the data transfers by the particularFIFO stages. In particular the external bus systems (0808/0809) mayoperate at a higher transfer rate, for example, than the internal bussystems (0104) and/or (0804).

FIG. 9 shows a possible sequence of a data read transfer via the circuitaccording to FIG. 8.

Addresses (preferably identifiers, e.g., with IOIDs and/or APIDs) aretransmitted via internal bus system 0104 to interface modules and/orPAEs having a dedicated global bus, which preferably have an internalFIFO (0901). The addresses are transmitted to an IO-FIFO (0903) via abus system (e.g., 0804) which preferably operates as a pipeline (0902).The addresses are transmitted to a BURST-FIFO (0905) via another bus(0904) which may be designed as a pipeline but which is preferably shortand local. The BURST-FIFO ensures correct handling of burst transfersvia the external bus system, e.g., for controlling burst addresses andburst sequences and repeating burst cycles when errors occur. IOIDsand/or APIDs of addresses (0906) which are transmitted via the externalbus system may be transmitted together with the addresses and/or storedin an additional SYNC-FIFO (0907). The SYNC-FIFO compensates for thelatency between the outgoing address (0906) and the incoming data(0909). Incoming data may be assigned IOIDs and/or APIDs (0908) of theaddresses referencing them via the SYNC-FIFO (0910). Data (andpreferably IOIDs and/or APIDs) is buffered in an IO-FIFO (0911) and issubsequently transmitted via a bus system (e.g., 0804), which preferablyfunctions as a pipeline (0912), to an interface module and/or PAE havinga dedicated global bus (0913), preferably including an internal FIFO.Data is transmitted from here to the internal bus system (0104).

Instead of to the IO-FIFO (0911), incoming data may optionally bedirected first to a second BURST-FIFO (not shown), which behaves likeBURST-FIFO 0905 if burst-error recovery is also necessary in readaccesses. Data is subsequently relayed to 0911.

FIG. 10 corresponds in principle to FIG. 8, which is why the samereference numbers have been used. In this embodiment, which is given asan example, fewer interface modules and/or PAEs having a dedicatedglobal bus (0801) and fewer protocol converters (0802) to external(main) memories and/or other (peripheral) data streams are shown. Inaddition, a collector (1001) is shown which is connected to bus systems0804 in such a way that data is written from the interface modules andprotocol converters into the collector and/or is read out from thecollector. The collector is switched to bus systems 0804 a viatriggering unit 1007 which corresponds to 0807, and the collector isswitched to bus systems 0804 b via triggering unit 1006, whichcorresponds to 0806.

Multiple collectors may be implemented for which multiple triggeringunits 1006 and 1007 are used.

A collector may be segmented into multiple memory areas. Each memoryarea may operate independently in different memory modes, e.g., asrandom access memory, FIFO, cache, MMU page, etc.

A translation table (TLB) (1002) may be assigned to a collector topermit an MMU-type mode of operation. Page management may function,e.g., on the basis of segment addresses and/or other identifiers, e.g.,APIDs and/or IOIDs.

A DMA or multiple DMAs are preferably assigned to a collector to performdata transfers with external (main) memories and/or other (peripheral)data streams, in particular to automatically permit the MMU function ofpage management (loading, writing). DMAs may also access the TLB foraddress translation between external (main) memories and/or other(peripheral) data streams and collector. In one possible mode ofoperation, DMAs may receive address specifications from the array (PA),e.g., via 0804.

DMAs may be triggered by one or more of the following units: an MMUassigned to the collector, e.g., in the case of page faults; the array(PA); an external bus (e.g., 0809); an external processor; ahigher-level loading unit (CT).

Collectors may have access to a dedicated bus interface (1004),preferably DMA-controlled and preferably master/slave capable, includinga protocol converter, corresponding to or similar to protocol converters0802 having access to external (main) memories and/or other (peripheral)data streams.

An external processor may have direct access to collectors (1007).

FIG. 11 corresponds in principle to FIG. 9, which is why the samereference numbers have been used. A collector (1101) including assignedtransfer control (e.g., DMA preferably with TLB) (1102) is integratedinto the data stream. The array (PA) now transmits data preferably usingthe collector (1103), which preferably exchanges data with external(main) memories and/or other (peripheral) data streams (1104), largelyautomatically and controlled via 1102. The collector preferablyfunctions in a segmented MMU-type mode of operation, where differentaddress areas and/or identifiers such as APIDs and/or IOIDs are assignedto different pages. Preferably 1102 may be controlled by page faults.

FIG. 12 shows a flow chart of data transfers for different applications.An array (PA) processes data according to the method described in GermanPatent Application No. DE 196 54 846.2 by storing operands and resultsin memories 1202 and 1203. In addition, a data input channel (1204) anda data output channel (1205) are assigned to the PA, through which theoperands and/or results are loaded and/or stored. The channels may leadto external (main) memories and/or other (peripheral) data streams(1208). The channels may include internal FIFO stages and/orPAE-RAMs/PAE-RAM pages and/or collectors/collector pages. The addresses(CURR-ADR) may be computed currently by a configuration running in 1201and/or may be computed in advance and/or computed by DMA operations of a(1003). In particular, an address computation within 1201 (CURR-ADR) maybe sent to a collector or its DMA to address and control the datatransfers of the collector. The data input channel may be preloaded by aconfiguration previously executed on 1201.

The channels preferably function in a FIFO-like mode of operation toperform data transfers with 1208.

In the example depicted here, a channel (1207), which has been filled bya previous configuration or application, is still being written to 1208during data processing within 1201 described here. This channel may alsoinclude internal FIFO stages and/or PAE-RAMs/PAE-RAM pages and/orcollectors/collector pages. The addresses may be computed currently by aconfiguration (OADR-CONF) running in parallel in 1201 and/or computed inadvance and/or computed by DMA operations of a (1003). In particular, anaddress computation within 1201 (OADR-CONF) may be sent to a collectoror its DMA to address and control the data transfers of the collector.

In addition, data for a subsequent configuration or application issimultaneously loaded into another channel (1206). This channel too mayinclude internal FIFO stages and/or PAE-RAMs/PAE-RAM pages and/orcollectors/collector pages. The addresses may be computed currently by aconfiguration (IADR-CONF) running in parallel in 1201 and/or computed inadvance and/or computed by DMA operations of a (1003). In particular, anaddress computation within 1201 (IADR-CONF) may be sent to a collectoror its DMA to address and control the data transfers of the collector.Individual entries into the particular channels may have differentidentifiers, e.g., IOIDs and/or APIDs, enabling them to be assigned to acertain resource and/or memory location. FIG. 13 a shows a preferredimplementation of a BURST-FIFO.

The function of an output FIFO which transmits its values to aburst-capable bus (BBUS) is to be described first. A first pointer(1301) points to the data entry within a memory (1304) currently to beoutput to the BBUS. With each data word output (1302), 1301 is moved byone position. The value of pointer 1301 prior to the start of thecurrent burst transfer has been stored in a register (1303). If an erroroccurs during the burst transfer, 1301 is reloaded with the originalvalue from 1303 and the burst transfer is restarted.

A second pointer (1305) points to the current data input position in thememory (1304) for data to be input (1306). To prevent overwriting of anydata still needed in the event of an error, pointer 1305 is compared(1307) with register 1303 to indicate that the BURST-FIFO is full. Theempty state of the BURST-FIFO may be ascertained by comparison (1308) ofthe output pointer (1301) with the input pointer (1305).

If the BURST-FIFO operates for input data from a burst transfer, thefunctions change as follows:

1301 becomes the input pointer for data 1306. If faulty data has beentransmitted during the burst transfer, the position prior to the bursttransfer is stored in 1303. If an error occurs during the bursttransfer, 1301 is reloaded with the original value from 1303 and theburst transfer is restarted.

The pointer points to the readout position of the BURST-FIFO for readingout the data (1302). To prevent premature readout of data of a bursttransfer that has not been concluded correctly, 1305 is compared withthe position stored in 1303 (1307) to indicate an empty BURST-FIFO. Afull BURST-FIFO is recognized by comparison (1308) of input pointer 1301with the output pointer (1305).

FIG. 13 b shows one possible implementation of a burst circuit whichrecognizes possible burst transfers and tests boundary limits. Theimplementation has been kept simple and recognizes only linear addresssequences. Data transfers are basically started as burst transfers. Theburst transfer is aborted at the first nonlinear address. Bursttransfers of a certain length (e.g., 4) may also be detected andinitialized by expanding a look-ahead logic, which checks multipleaddresses in advance.

The address value (1313) of a first access is stored in a register(1310). The address value of a subsequent data transfer is compared(1312) with the address value (1311) of 1310, which has been incrementedby the address difference between the first data transfer and the seconddata transfer of the burst transfer (typically one word wide). If thetwo values are the same, then the difference between the first addressand the second address corresponds to the address difference of theburst transfer between two burst addresses. Thus, this is a correctburst. If the values are not the same, the burst transfer must beaborted.

The last address (1313) checked (the second address in the writing) isstored in 1310 and then compared with the next address (1313)accordingly.

To ascertain whether the burst limits (boundaries) have been maintained,the address bit(s) at which the boundary of the current address value(1313) is located is (are) compared with the address bits of thepreceding address value (1310) (e.g., XOR 1314). If the address bits arenot the same, the boundary has been exceeded and the control of theburst must respond accordingly (e.g., termination of the burst transferand restart).

FIG. 14 shows as an example various methods of connecting memories, inparticular PAE-RAMs, to form a larger cohesive memory block.

FIGS. 14 a-14 d use the same reference numbers whenever possible.

Write data (1401) is preferably sent to the memories via pipeline stages(1402). Read data (1403) is preferably removed from the memories alsovia pipeline stages (1404). Pipeline stage 1404 includes a multiplexer,which forwards the particular active data path. The active data path maybe recognized, for example, by a RDY handshake applied.

A unit (RangeCheck, 1405) for monitoring the addresses (1406) forcorrect values within the address space may optionally be provided.

In FIG. 14 a, the addresses are sent to the memories (1408 a) viapipeline stages (1407 a). The memories compare the higher-value addresspart with a fixedly predetermined or configurable (e.g., by ahigher-level configuration unit CT) reference address, which is uniquefor each memory. If they are identical, that memory is selected. Thelower-value address part is used for selection of the memory location inthe memory.

In FIG. 14 b, the addresses are sent to the memories (1408 b) viapipeline stages having an integrated decrementer (subtraction by 1)(1407 b). The memories compare the higher-value address part with thevalue zero. If they are identical, that memory is selected. Thelower-value address part is used for selection of the memory location inthe memory.

In FIG. 14 c, the addresses are sent to the memories (1408 c) viapipeline stages (1407 c). The memories compare the higher-level addresspart with a reference address, which is unique for each memory. Thereference address is generated by an adding or subtracting chain (1409),which preselects another unique reference address for each memory on thebasis of a starting value (typically 0). If they are identical, thatmemory is selected. The lower-value address part is used for selectionof the memory location in the memory.

In FIG. 14 d, the addresses are sent to the memories (1408 d) viapipeline stages (1407 d). The memories compare the higher-value addresspart with a reference address which is unique for each memory. Thereference address is generated by an addressing or subtracting chain(1410), which is integrated into the memories and preselects anotherunique reference address for each memory on the basis of a startingvalue (typically 0). If they are identical, that memory is selected. Thelower-value address part is used for selection of the memory location inthe memory.

For example, FREGs of the PAEs according to FIG. 5 may be used for 1402,1404, and 1407. Depending on the direction of travel of the referenceaddress, FREG or BREG may be used for 1409. The design shown here as anexample has the advantage in particular that all the read/write accesseshave the same latency because the addresses and data are sent to theBREG/FREG via register stages.

FIG. 15 shows the use of GlobalTrack bus systems (1501, 1502, 1503,1504) for coupling configurations which were configured in any way asconfiguration macros (1506, 1507) within a system of PAEs (1505) (seealso DE 198 07 872.2, DE 199 26 538.0, DE 100 28 397.7). Theconfiguration macros have (1508) their own internal bus connections,e.g., via internal buses (0104). The configuration macros areinterconnected via 1503 for data exchange. 1506 is connected tointerface modules and/or local memories (RAM-PAEs) (1509, 1510) via1501, 1502. 1507 is connected to interface modules and/or local memories(RAM-PAEs) (1511) via 1504.

Any other embodiments and combinations of the present inventionsdescribed here are possible and are self-evident in view of theforegoing, to those skilled in the art.

1. A method of transmitting data streams between (a) a reconfigurableprocessor device including an at least two-dimensional matrix ofconfigurable elements having arithmetic logic units (ALUs) and (b)devices that are external to the reconfigurable processor device, themethod comprising: using at least one address generator, generatingaddresses according to which the external data streams are addressed;and at least one of: (a) buffering write data streams by storing outputwrite addresses and corresponding output write data in a FIFO memorysystem; and (b) buffering read data streams by storing output readaddresses and input read data in the FIFO memory system.
 2. The methodas recited in claim 1, wherein a plurality of independent addressgenerators are used.
 3. The method as recited in claim 2, wherein theaddress generators are one of (a) configured independently of dataprocessing and (b) hardwired.
 4. The method as recited in claim 3wherein address calculations for a plurality of configurations aredetermined at compile time prior to processing of data streams whichoccurs according to the compile.
 5. The method as recited in claim 4,further comprising: determining data that will be needed in futureconfigurations that are executed; and preloading respective data of thedetermined data into memories one of (a) prior to and (b) during theexecution of respective ones of the future configurations.
 6. The methodas recited in claim 3, further comprising: determining data that will beneeded in future configurations that are executed; and preloadingrespective data of the determined data into memories one of (a) prior toand (b) during the execution of respective ones of the futureconfigurations.
 7. The method as recited in claim 2, wherein addresscalculations for a plurality of configurations are determined at compiletime prior to processing of data streams which occurs according to thecompile.
 8. The method as recited in claim 7, further comprising:determining data that will be needed in future configurations that areexecuted; and preloading respective data of the determined data intomemories one of (a) prior to and (b) during the execution of respectiveones of the future configurations.
 9. The method as recited in claim 1,wherein address calculations for a plurality of configurations aredetermined at compile time prior to processing of data streams whichoccurs according to the compile.
 10. The method as recited in claim 9,further comprising: determining data that will be needed in futureconfigurations that are executed; and preloading respective data of thedetermined data into memories one of (a) prior to and (b) during theexecution of respective ones of the future configurations.
 11. Themethod as recited in claim 1, further comprising: determining data thatwill be needed in future configurations that are executed; andpreloading respective data of the determined data into memories one of(a) prior to and (b) during the execution of respective ones of thefuture configurations.
 12. The method as recited in claim 2, furthercomprising: determining data that will be needed in futureconfigurations that are executed; and preloading respective data of thedetermined data into memories one of (a) prior to and (b) during theexecution of respective ones of the future configurations.
 13. Themethod as recited in claim 1, wherein: at least one of the data streamsis a stream of external data that is directed into the matrix array andis addressed to an element of the matrix array.
 14. The method asrecited in claim 1, wherein at least one of the data streams is a streamof external data directed away from the matrix array into a devicedifferent from the matrix array.
 15. The method as recited in any one ofclaims 2 to 11 and 7 to 10, wherein: data for an external data stream isgenerated by configured elements of the array, is stored in the FIFOmemory, and remains stored in the FIFO memory while at least one of theelements of the array which generated the data is reconfigured; and themethod further comprises: streaming data out of the FIFO memory as anexternal data stream to a receiver; and receiving an acknowledgement ofcorrect receipt of the data streamed to the receiver.
 16. The method asrecited in claim 15, further comprising: preventing at least one of (a)erasure and (b) overwriting of the generated data stored in the FIFOmemory if the generated data has been sent but receipt of the generatedhas not been acknowledged.